feat: add piece_count and piece_size fields to BomItem for cut-to-length parts by amanjain57-gif · Pull Request #12422 · inventree/InvenTree

amanjain57-gif · 2026-07-19T00:24:39Z

Summary

Addresses #10274

Manufacturing BOMs frequently require multiple pieces of a specific size cut from continuous stock (cables, tubing,
structural profiles). Currently the only way to express "10 pieces of 250mm cable" is to enter the total length (2.5m)
as quantity, which loses the piece-count information that purchasing and production need.

Changes

Adds two optional fields to BomItem:

piece_count: number of discrete pieces required (default: 1)
piece_size: size/length of each piece (e.g. "250 mm")

When piece_size is specified, the total quantity is auto-calculated as piece_count × piece_size, maintaining full
backward compatibility (existing items effectively have piece_count=1 and empty piece_size).

Backend

New model fields with migration
Updated recalculate_quantity() to compute total from piece_count × piece_size when piece_size is set
Added fields to BOM item hash for validation checksum

API

Serializer exposes piece_count and piece_size fields

Frontend

BOM creation/edit form includes the new fields
BOM table shows piece_count and piece_size as optional (hidden by default) columns

Example

A BOM line for "10 pieces of 250mm aluminum profile" (part units: m):

piece_count: 10
piece_size: "250 mm"
Auto-calculated quantity: 2.5 (meters)

This preserves the per-piece information for production while correctly computing total material requirement for
purchasing.

…gth parts Manufacturing BOMs frequently require multiple pieces of a specific size cut from continuous stock (cables, tubing, structural profiles). Currently the only way to express "10 pieces of 250mm cable" is to enter the total length (2.5m) as quantity, which loses the piece-count information that purchasing and production need. This adds two optional fields to BomItem: - piece_count: number of discrete pieces required (default: 1) - piece_size: size/length of each piece (e.g. "250 mm") When piece_size is specified, the total quantity is auto-calculated as piece_count × piece_size, maintaining full backward compatibility (existing items effectively have piece_count=1 and empty piece_size). Changes: - Backend: new model fields, migration, updated recalculate_quantity() logic, hash_fields for BOM validation - API: serializer exposes piece_count and piece_size - Frontend: BOM form includes the new fields, BOM table shows them as optional columns Addresses inventree#10274

netlify · 2026-07-19T00:24:44Z

✅ Deploy Preview for inventree-web-pui-preview canceled.

Name	Link
🔨 Latest commit	`8d92cc4`
🔍 Latest deploy log	https://app.netlify.com/projects/inventree-web-pui-preview/deploys/6a807c47ef2a5b00082ca9c6

SchrodingersGat · 2026-07-27T01:50:51Z

@amanjain57-gif an interesting idea here, thanks for submitting.

I think that you can achieve this with a single additional field, not two.

If you remove the "piece_size" field and just use quantity, then the additional "piece_count" field can be used to reflect multiple pieces.

e.g. a BOM with multiple lengths of wire

Field	Value	Description
quantity	200mm	Length of individual cut wires
piece_count	10	10x separate multiples of 200mm

Thus the total requirement is 2m of wire, but we can see it is in 10x pieces of 200mm

SchrodingersGat

Reduce to a single additional field as discussed

Remove the piece_size field entirely. The existing quantity field already represents the per-piece size/length, so piece_count multiplied by quantity gives the total material requirement. Example: quantity=200mm, piece_count=10 → total 2m of wire in 10 pieces. Changes: - Remove piece_size model field, serializer field, and frontend column/form - Update migration to only add piece_count - Update get_required_quantity() to multiply by piece_count - Restore original recalculate_quantity() without piece_size logic

amanjain57-gif · 2026-07-28T17:48:00Z

Thanks for the feedback! Simplified to a single piece_count field as suggested. quantity now represents per-piece size, and total material = quantity × piece_count. Removed piece_size from model, migration, serializer, and frontend.

SchrodingersGat · 2026-07-29T09:51:04Z

@amanjain57-gif thanks for the updates.

Can you please also add some unit tests here, for (at least) the following:

Expected "quantity required" calculations based on the new field
API GET / POST tests for the new field

SchrodingersGat · 2026-07-31T09:59:15Z

You will also need to add comprehensive documentation for the new extension

amanjain57-gif · 2026-08-02T14:37:53Z

@SchrodingersGat Working on both requests:

Unit tests — Adding tests for get_required_quantity() calculations with piece_count, API GET/POST/PATCH tests for the new field, and validation tests (default=1, positive-only).
Documentation — Adding a section to the BOM docs explaining piece_count with examples (e.g., quantity=200mm, piece_count=10, total=2m of wire).

Will push shortly.

amanjain57-gif · 2026-08-02T14:39:27Z

Done — pushed unit tests and documentation:

Tests added (11 total):

6 model-level tests: default value, quantity multiplier calculation, interactions with attrition/setup_quantity/rounding, and validation (rejects 0 and negatives)
5 API tests: GET returns piece_count, POST with/without piece_count, PATCH updates, invalid values return 400

Documentation:

Added piece_count to the BOM Line Items table in docs/docs/manufacturing/bom.md
Added a "Piece Count (Cut-to-Length Parts)" section with the formula, two worked examples (wire harness, hydraulic tubing with attrition), and usage tips
Added to BOM Checksum fields list

amanjain57-gif · 2026-08-03T04:51:46Z

Fixed ruff check failure — replaced Unicode multiplication sign (×) with plain x in docstrings (RUF002).

SchrodingersGat · 2026-08-07T23:57:27Z

@amanjain57-gif looking good! Please fix:

Add an entry to api_version.py
Add an entry to CHANGELOG.md
Fix style issues

- Bump INVENTREE_API_VERSION to 531 with entry for piece_count field - Add CHANGELOG.md entry under Unreleased > Added - Fix RUF001: replace ambiguous × with x in serializers.py help_text

amanjain57-gif · 2026-08-10T16:33:53Z

@SchrodingersGat Thanks — all three addressed:

api_version.py — bumped to v531 with an entry for the new piece_count field.
CHANGELOG.md — added an entry under Unreleased → Added.
Style — fixed the remaining RUF001 (ambiguous × → x) in the piece_count serializer help text. ruff check + ruff format --preview (v0.15.12, matching .pre-commit-config.yaml) are clean locally.

The API Schema check should also resolve now, since the version bump lets the paths filter pick up the API change.

SchrodingersGat · 2026-08-11T02:01:51Z

@amanjain57-gif nice, this is looking pretty clean now

SchrodingersGat · 2026-08-11T03:17:57Z

Still need to address outstanding CI failures

The 0153 AddField recorded help_text with a Unicode multiplication sign (×), while the model field uses plain 'x' after the RUF001 fix. This mismatch made makemigrations --check flag an unstaged 0154_alter_bomitem_piece_count migration, failing the DB test CI jobs. Update the original migration's help_text (and docstring) to plain 'x' so the field definition matches the model, keeping a single clean migration instead of add-then-alter.

amanjain57-gif · 2026-08-12T09:34:17Z

@SchrodingersGat Fixed the outstanding CI failure. The DB test jobs were failing on the unstaged-migration check:

There are 1 unstaged migration files:
 - src/backend/InvenTree/part/migrations/0154_alter_bomitem_piece_count.py

Root cause: migration 0153's AddField still recorded the help_text with a Unicode ×, while the model field was switched to plain x in the RUF001 fix. That one-character mismatch made makemigrations --check want a redundant alter_bomitem_piece_count migration.

Since piece_count is new in this PR, I updated the original 0153 migration's help_text (and docstring) to plain x so it matches the model — keeping a single clean migration rather than add-then-alter. Field definitions now match, so the check should pass. (The earlier lone Frontend Firefox failure looked flaky/unrelated to this backend change.)

codecov · 2026-08-12T13:52:50Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.81%. Comparing base (e4b23b4) to head (8d92cc4).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #12422      +/-   ##
==========================================
- Coverage   86.83%   86.81%   -0.03%     
==========================================
  Files        1449     1450       +1     
  Lines       96884    96982      +98     
  Branches    11185    11271      +86     
==========================================
+ Hits        84132    84195      +63     
- Misses      12688    12723      +35     
  Partials       64       64

Flag	Coverage Δ
backend	`90.84% <100.00%> (+<0.01%)`	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Backend Apps	`92.22% <100.00%> (+<0.01%)`	⬆️
Backend General	`93.75% <ø> (-0.04%)`	⬇️
Frontend	`79.66% <ø> (-0.07%)`	⬇️

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

BomItem.quantity is a derived field, recalculated from raw_amount on every save() via recalculate_quantity(). Setting item.quantity directly was overwritten back to the fixture value on save, so the tests computed against quantity=3 and failed. Use set_quantity() (which sets raw_amount) to match how quantity is meant to be updated.

amanjain57-gif · 2026-08-12T15:21:58Z

Fixed the 5 failing test_bom_item tests. Root cause: BomItem.quantity is a derived field — it's recalculated from raw_amount on every save() via recalculate_quantity(). The tests set item.quantity = N directly, which got overwritten back to the fixture value on save, so get_required_quantity() was computing against the wrong quantity.

Switched them to item.set_quantity(N) (which sets raw_amount), matching how quantity is meant to be updated elsewhere. The piece_count multiplier logic itself was correct.

SchrodingersGat · 2026-08-14T07:16:25Z

@amanjain57-gif you will need to address the conflict here due to API version updates

…o-length-parts # Conflicts: # src/backend/InvenTree/InvenTree/api_version.py

amanjain57-gif · 2026-08-15T07:45:36Z

@SchrodingersGat Conflict resolved — merged latest master. Upstream had taken v531 (PR #12635), so I moved the piece_count entry to v532 and bumped INVENTREE_API_VERSION accordingly. Branch is mergeable again.

amanjain57-gif · 2026-08-15T14:28:26Z

Heads up on CI: the only red check is Tests [Firefox 1 / 2], and the three failures are the known-flaky Firefox E2E specs — pui_dashboard.spec.ts › Dashboard - Basic and pui_build.spec.ts › Build Order - {Build Outputs, Consume Stock} — all failing with locator.waitFor/click: Test ended plus Firefox juggler/favicon browser errors. None touch BomItem/piece_count, and Firefox 2 / 2 passed. Looks related to the flaky-Firefox work in #12640. A re-run should clear it (I don't have permissions to trigger one). Happy to rebase if that helps.

matmair · 2026-08-15T14:44:54Z

That pr is already in your branch; I am not sure how a rerun would help

amanjain57-gif · 2026-08-15T14:48:42Z

You're right — #12640 is already in the branch from the master merge, so a re-run wouldn't pull in anything new. My mistake referencing it; it also only touched pui_transfer.spec.ts, which isn't one of the failing specs.

What I actually meant is that the three failures (pui_dashboard.spec.ts › Dashboard - Basic, pui_build.spec.ts › Build Order - Build Outputs / Consume Stock) look like transient Firefox E2E failures — they die with locator.waitFor/click: Test ended alongside Firefox juggler/favicon browser errors rather than assertion failures, and none of them exercise the piece_count change (a BomItem model/serializer field plus a BomTable column). Firefox 2 / 2 passed.

I've pushed a fresh commit to trigger a clean run — let's see if they come back green. If you're seeing these as genuinely caused by this PR rather than environmental, I'd appreciate a pointer and I'll dig in; I can't reproduce Firefox E2E reliably locally.

SchrodingersGat · 2026-08-15T23:43:38Z

@amanjain57-gif please note that in future I have no interest in a discussion with your AI agent.

* [bug] OptionalField race condition (inventree#12627) * [bug] OptionalField race condition Fixes subtle bug where OptionalField entries can be silenty dropped from an API request due to concurrent requests / race conditions * Additional unit tests * Additional guard in metadata.py * include extra kwargs * Adjust import/exporting options * Fix attribute sharing across class instances * reset errors on update (inventree#12550) * reset errors on update * add empty line --------- Co-authored-by: Oliver <oliver.henry.walters@gmail.com> * Add docs for return order (inventree#12632) * [bug] Fix ReturnOrder event registration (inventree#12633) * Allow bulk-edit for ReturnOrderLineItem (inventree#12635) * Allow bulk-edit for ReturnOrderLineItem - Allow bulk change of line item outcome * Update API version documentation with pull request links * [bug] Fix broken user setting (inventree#12638) - Closes inventree#12637 * try fixing this flaky test on firefox (inventree#12640) * feat: add piece_count and piece_size fields to BomItem for cut-to-length parts (inventree#12422) * feat: add piece_count and piece_size fields to BomItem for cut-to-length parts Manufacturing BOMs frequently require multiple pieces of a specific size cut from continuous stock (cables, tubing, structural profiles). Currently the only way to express "10 pieces of 250mm cable" is to enter the total length (2.5m) as quantity, which loses the piece-count information that purchasing and production need. This adds two optional fields to BomItem: - piece_count: number of discrete pieces required (default: 1) - piece_size: size/length of each piece (e.g. "250 mm") When piece_size is specified, the total quantity is auto-calculated as piece_count × piece_size, maintaining full backward compatibility (existing items effectively have piece_count=1 and empty piece_size). Changes: - Backend: new model fields, migration, updated recalculate_quantity() logic, hash_fields for BOM validation - API: serializer exposes piece_count and piece_size - Frontend: BOM form includes the new fields, BOM table shows them as optional columns Addresses inventree#10274 * refactor: simplify to single piece_count field per reviewer feedback Remove the piece_size field entirely. The existing quantity field already represents the per-piece size/length, so piece_count multiplied by quantity gives the total material requirement. Example: quantity=200mm, piece_count=10 → total 2m of wire in 10 pieces. Changes: - Remove piece_size model field, serializer field, and frontend column/form - Update migration to only add piece_count - Update get_required_quantity() to multiply by piece_count - Restore original recalculate_quantity() without piece_size logic * test/docs: add unit tests and documentation for piece_count field * style: replace ambiguous × with x to fix RUF002 lint error * Address review feedback: api_version bump, changelog, style fix - Bump INVENTREE_API_VERSION to 531 with entry for piece_count field - Add CHANGELOG.md entry under Unreleased > Added - Fix RUF001: replace ambiguous × with x in serializers.py help_text * fix: align piece_count migration help_text with model (RUF001) The 0153 AddField recorded help_text with a Unicode multiplication sign (×), while the model field uses plain 'x' after the RUF001 fix. This mismatch made makemigrations --check flag an unstaged 0154_alter_bomitem_piece_count migration, failing the DB test CI jobs. Update the original migration's help_text (and docstring) to plain 'x' so the field definition matches the model, keeping a single clean migration instead of add-then-alter. * fix: use set_quantity() in piece_count tests BomItem.quantity is a derived field, recalculated from raw_amount on every save() via recalculate_quantity(). Setting item.quantity directly was overwritten back to the fixture value on save, so the tests computed against quantity=3 and failed. Use set_quantity() (which sets raw_amount) to match how quantity is meant to be updated. * ci: re-trigger CI to confirm Firefox E2E failures are transient --------- Co-authored-by: Aman Jain <jainamn@amazon.com> * Improve error handling for unit registry (inventree#12643) * New Crowdin translations by GitHub Action (inventree#12625) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * chore(deps): bump the dependencies group across 1 directory with 6 updates (inventree#12651) Bumps the dependencies group with 6 updates in the /src/frontend directory: | Package | From | To | | --- | --- | --- | | [@codemirror/view](https://github.com/codemirror/view) | `6.43.7` | `6.43.8` | | [@sentry/react](https://github.com/getsentry/sentry-javascript) | `10.69.0` | `10.70.0` | | [react-hook-form](https://github.com/react-hook-form/react-hook-form) | `7.84.0` | `7.85.0` | | [styled-components](https://github.com/styled-components/styled-components) | `6.4.4` | `6.5.1` | | [@flakiness/playwright](https://github.com/flakiness/playwright) | `2.0.1` | `2.0.2` | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.1.2` | `26.2.0` | Updates `@codemirror/view` from 6.43.7 to 6.43.8 - [Changelog](https://github.com/codemirror/view/blob/main/CHANGELOG.md) - [Commits](https://github.com/codemirror/view/commits) Updates `@sentry/react` from 10.69.0 to 10.70.0 - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/10.70.0/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@10.69.0...10.70.0) Updates `react-hook-form` from 7.84.0 to 7.85.0 - [Release notes](https://github.com/react-hook-form/react-hook-form/releases) - [Changelog](https://github.com/react-hook-form/react-hook-form/blob/master/CHANGELOG.md) - [Commits](react-hook-form/react-hook-form@v7.84.0...v7.85.0) Updates `styled-components` from 6.4.4 to 6.5.1 - [Release notes](https://github.com/styled-components/styled-components/releases) - [Commits](https://github.com/styled-components/styled-components/compare/styled-components@6.4.4...styled-components@6.5.1) Updates `@flakiness/playwright` from 2.0.1 to 2.0.2 - [Release notes](https://github.com/flakiness/playwright/releases) - [Commits](flakiness/playwright@v2.0.1...v2.0.2) Updates `@types/node` from 26.1.2 to 26.2.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@codemirror/view" dependency-version: 6.43.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: "@sentry/react" dependency-version: 10.70.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: react-hook-form dependency-version: 7.85.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: styled-components dependency-version: 6.5.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: "@flakiness/playwright" dependency-version: 2.0.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: "@types/node" dependency-version: 26.2.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: dependencies ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump the dependencies group with 5 updates (inventree#12652) Bumps the dependencies group with 5 updates: | Package | From | To | | --- | --- | --- | | [dorny/paths-filter](https://github.com/dorny/paths-filter) | `4.0.2` | `4.0.3` | | [oasdiff/oasdiff-action/diff](https://github.com/oasdiff/oasdiff-action) | `0.1.11` | `0.1.12` | | [CodSpeedHQ/action](https://github.com/codspeedhq/action) | `5.0.2` | `5.0.3` | | [actions/attest](https://github.com/actions/attest) | `4.2.1` | `4.2.2` | | [github/codeql-action/upload-sarif](https://github.com/github/codeql-action) | `4.37.5` | `4.37.6` | Updates `dorny/paths-filter` from 4.0.2 to 4.0.3 - [Release notes](https://github.com/dorny/paths-filter/releases) - [Changelog](https://github.com/dorny/paths-filter/blob/master/CHANGELOG.md) - [Commits](dorny/paths-filter@7b450ff...ceb8a2b) Updates `oasdiff/oasdiff-action/diff` from 0.1.11 to 0.1.12 - [Release notes](https://github.com/oasdiff/oasdiff-action/releases) - [Commits](oasdiff/oasdiff-action@b7c3ade...033c15c) Updates `CodSpeedHQ/action` from 5.0.2 to 5.0.3 - [Release notes](https://github.com/codspeedhq/action/releases) - [Changelog](https://github.com/CodSpeedHQ/action/blob/main/CHANGELOG.md) - [Commits](CodSpeedHQ/action@0ca9cbb...4296e51) Updates `actions/attest` from 4.2.1 to 4.2.2 - [Release notes](https://github.com/actions/attest/releases) - [Changelog](https://github.com/actions/attest/blob/main/RELEASE.md) - [Commits](actions/attest@508db95...1e69f48) Updates `github/codeql-action/upload-sarif` from 4.37.5 to 4.37.6 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@d1ba80a...5595cca) --- updated-dependencies: - dependency-name: dorny/paths-filter dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: oasdiff/oasdiff-action/diff dependency-version: 0.1.12 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: CodSpeedHQ/action dependency-version: 5.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: actions/attest dependency-version: 4.2.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: github/codeql-action/upload-sarif dependency-version: 4.37.6 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump the dependencies group across 1 directory with 14 updates (inventree#12642) * chore(deps): bump the dependencies group across 1 directory with 14 updates Bumps the dependencies group with 14 updates in the /src/backend directory: | Package | From | To | | --- | --- | --- | | [cffi](https://github.com/python-cffi/cffi) | `2.1.0` | `2.1.1` | | [coverage](https://github.com/coveragepy/coveragepy) | `7.15.2` | `7.15.4` | | [django-stubs](https://github.com/typeddjango/django-stubs) | `6.0.7` | `6.0.9` | | [django-stubs-ext](https://github.com/typeddjango/django-stubs) | `6.0.6` | `6.0.9` | | [django-test-migrations](https://github.com/wemake-services/django-test-migrations) | `1.5.0` | `1.6.0` | | [packaging](https://github.com/pypa/packaging) | `26.2` | `26.3` | | [pip](https://github.com/pypa/pip) | `26.2` | `26.2.1` | | [prek](https://github.com/j178/prek) | `0.4.11` | `0.4.12` | | [pytest-django](https://github.com/pytest-dev/pytest-django) | `4.12.0` | `4.13.0` | | [blessed](https://github.com/jquast/blessed) | `1.47.0` | `1.48.0` | | [boto3](https://github.com/boto/boto3) | `1.43.61` | `1.43.66` | | [botocore](https://github.com/boto/botocore) | `1.43.61` | `1.43.66` | | [djangorestframework](https://github.com/encode/django-rest-framework) | `3.17.1` | `3.18.0` | | [googleapis-common-protos](https://github.com/googleapis/google-cloud-python) | `1.75.0` | `1.75.1` | Updates `cffi` from 2.1.0 to 2.1.1 - [Release notes](https://github.com/python-cffi/cffi/releases) - [Commits](python-cffi/cffi@v2.1.0...v2.1.1) Updates `coverage` from 7.15.2 to 7.15.4 - [Release notes](https://github.com/coveragepy/coveragepy/releases) - [Changelog](https://github.com/coveragepy/coveragepy/blob/main/CHANGES.rst) - [Commits](coveragepy/coveragepy@7.15.2...7.15.4) Updates `django-stubs` from 6.0.7 to 6.0.9 - [Release notes](https://github.com/typeddjango/django-stubs/releases) - [Commits](typeddjango/django-stubs@6.0.7...6.0.9) Updates `django-stubs-ext` from 6.0.6 to 6.0.9 - [Release notes](https://github.com/typeddjango/django-stubs/releases) - [Commits](typeddjango/django-stubs@6.0.6...6.0.9) Updates `django-test-migrations` from 1.5.0 to 1.6.0 - [Release notes](https://github.com/wemake-services/django-test-migrations/releases) - [Changelog](https://github.com/wemake-services/django-test-migrations/blob/master/CHANGELOG.md) - [Commits](wemake-services/django-test-migrations@1.5.0...1.6.0) Updates `packaging` from 26.2 to 26.3 - [Release notes](https://github.com/pypa/packaging/releases) - [Changelog](https://github.com/pypa/packaging/blob/main/CHANGELOG.rst) - [Commits](pypa/packaging@26.2...26.3) Updates `pip` from 26.2 to 26.2.1 - [Changelog](https://github.com/pypa/pip/blob/main/NEWS.rst) - [Commits](pypa/pip@26.2...26.2.1) Updates `prek` from 0.4.11 to 0.4.12 - [Release notes](https://github.com/j178/prek/releases) - [Changelog](https://github.com/j178/prek/blob/master/CHANGELOG.md) - [Commits](j178/prek@v0.4.11...v0.4.12) Updates `pytest-django` from 4.12.0 to 4.13.0 - [Release notes](https://github.com/pytest-dev/pytest-django/releases) - [Changelog](https://github.com/pytest-dev/pytest-django/blob/main/docs/changelog.rst) - [Commits](pytest-dev/pytest-django@v4.12.0...v4.13.0) Updates `blessed` from 1.47.0 to 1.48.0 - [Release notes](https://github.com/jquast/blessed/releases) - [Changelog](https://github.com/jquast/blessed/blob/master/docs/history.rst) - [Commits](https://github.com/jquast/blessed/commits/1.48) Updates `boto3` from 1.43.61 to 1.43.66 - [Release notes](https://github.com/boto/boto3/releases) - [Commits](boto/boto3@1.43.61...1.43.66) Updates `botocore` from 1.43.61 to 1.43.66 - [Commits](boto/botocore@1.43.61...1.43.66) Updates `djangorestframework` from 3.17.1 to 3.18.0 - [Release notes](https://github.com/encode/django-rest-framework/releases) - [Commits](encode/django-rest-framework@3.17.1...3.18.0) Updates `googleapis-common-protos` from 1.75.0 to 1.75.1 - [Release notes](https://github.com/googleapis/google-cloud-python/releases) - [Changelog](https://github.com/googleapis/google-cloud-python/blob/main/packages/google-cloud-documentai/CHANGELOG.md) - [Commits](googleapis/google-cloud-python@googleapis-common-protos-v1.75.0...googleapis-common-protos-v1.75.1) --- updated-dependencies: - dependency-name: cffi dependency-version: 2.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: coverage dependency-version: 7.15.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: django-stubs dependency-version: 6.0.9 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: django-stubs-ext dependency-version: 6.0.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: django-test-migrations dependency-version: 1.6.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: packaging dependency-version: '26.3' dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: pip dependency-version: 26.2.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: prek dependency-version: 0.4.12 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: pytest-django dependency-version: 4.13.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: blessed dependency-version: 1.48.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: boto3 dependency-version: 1.43.66 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: botocore dependency-version: 1.43.66 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies - dependency-name: djangorestframework dependency-version: 3.18.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dependencies - dependency-name: googleapis-common-protos dependency-version: 1.75.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dependencies ... Signed-off-by: dependabot[bot] <support@github.com> * fix style --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Matthias Mair <code@mjmair.com> * Fix issue 10769 (inventree#12286) * fix: Show badges for flagged stock items * Updated badge logic to only display on build order and sales order * refactor: Remove unused modelRenderer for RenderStockItem in BuildForms and SalesOrderForms * [FR] stop shipping docs with packages Fixes inventree#12610 --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: Oliver <oliver.henry.walters@gmail.com> Co-authored-by: ribsey <lukas.ribi@gmail.com> Co-authored-by: amanjain57-gif <aman.jain57@gmail.com> Co-authored-by: Aman Jain <jainamn@amazon.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Alonso Lopez-Valdez <alonsl1@uci.edu>

amanjain57-gif requested a review from SchrodingersGat as a code owner July 19, 2026 00:24

SchrodingersGat requested changes Jul 27, 2026

View reviewed changes

Merge branch 'master' into feature/bom-cut-to-length-parts

cdcf59f

test/docs: add unit tests and documentation for piece_count field

2c4caed

style: replace ambiguous × with x to fix RUF002 lint error

11010ee

Address review feedback: api_version bump, changelog, style fix

f8b5d5d

- Bump INVENTREE_API_VERSION to 531 with entry for piece_count field - Add CHANGELOG.md entry under Unreleased > Added - Fix RUF001: replace ambiguous × with x in serializers.py help_text

SchrodingersGat added this to the 1.6.0 milestone Aug 11, 2026

SchrodingersGat added enhancement This is an suggested enhancement or new feature api Relates to the API User Interface Related to the frontend / User Interface labels Aug 11, 2026

SchrodingersGat approved these changes Aug 11, 2026

View reviewed changes

Merge remote-tracking branch 'upstream/master' into feature/bom-cut-t…

affc31e

…o-length-parts # Conflicts: # src/backend/InvenTree/InvenTree/api_version.py

ci: re-trigger CI to confirm Firefox E2E failures are transient

8d92cc4

SchrodingersGat merged commit ee4ad7f into inventree:master Aug 15, 2026
46 checks passed

Uh oh!

Uh oh!

Conversation

amanjain57-gif commented Jul 19, 2026

Summary

Changes

Backend

API

Frontend

Example

Uh oh!

netlify Bot commented Jul 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for inventree-web-pui-preview canceled.

Uh oh!

SchrodingersGat commented Jul 27, 2026

Uh oh!

SchrodingersGat left a comment

Choose a reason for hiding this comment

Uh oh!

amanjain57-gif commented Jul 28, 2026

Uh oh!

SchrodingersGat commented Jul 29, 2026

Uh oh!

SchrodingersGat commented Jul 31, 2026

Uh oh!

amanjain57-gif commented Aug 2, 2026

Uh oh!

amanjain57-gif commented Aug 2, 2026

Uh oh!

amanjain57-gif commented Aug 3, 2026

Uh oh!

SchrodingersGat commented Aug 7, 2026

Uh oh!

amanjain57-gif commented Aug 10, 2026

Uh oh!

SchrodingersGat commented Aug 11, 2026

Uh oh!

SchrodingersGat commented Aug 11, 2026

Uh oh!

amanjain57-gif commented Aug 12, 2026

Uh oh!

codecov Bot commented Aug 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

amanjain57-gif commented Aug 12, 2026

Uh oh!

SchrodingersGat commented Aug 14, 2026

Uh oh!

amanjain57-gif commented Aug 15, 2026

Uh oh!

amanjain57-gif commented Aug 15, 2026

Uh oh!

matmair commented Aug 15, 2026

Uh oh!

amanjain57-gif commented Aug 15, 2026

Uh oh!

SchrodingersGat commented Aug 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

netlify Bot commented Jul 19, 2026 •

edited

Loading

codecov Bot commented Aug 12, 2026 •

edited

Loading